-
Notifications
You must be signed in to change notification settings - Fork 463
Display scmsync package actions #18372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hellcp-work-scmsync-package |
7966254 to
caab5fe
Compare
|
could you hide this version of the sources by default? These are not the sources which are processed when rpmbuild runs and neither what is maintained in git. Esp. when we start now using subdirectories it willl lead to confusion... so, maybe just collapsing it and show it only on request (mouse click). Also, the scmsync url itself seems not to be displayed. The showing URL is the project url from tag, right? |
Doable
It is, both in the project's package list and also in the top right (Developed at SCM link) |
|
| | Also, the scmsync url itself seems not to be displayed. The showing URL is the project url from tag, right? I see, maybe we can have that link more prominent by default. For example showing this one instead of the sources by default. |
caab5fe to
fa7caf0
Compare
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hellcp-work-scmsync-package |
2 similar comments
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hellcp-work-scmsync-package |
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hellcp-work-scmsync-package |
607d67a to
1294f76
Compare
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hellcp-work-scmsync-package |
7 similar comments
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hellcp-work-scmsync-package |
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hellcp-work-scmsync-package |
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hellcp-work-scmsync-package |
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hellcp-work-scmsync-package |
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hellcp-work-scmsync-package |
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hellcp-work-scmsync-package |
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hellcp-work-scmsync-package |
1294f76 to
c4389a5
Compare
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hellcp-work-scmsync-package |
09a5f37 to
0437cb8
Compare
0437cb8 to
cefbb90
Compare
| @package = Package.get_by_project_and_name(@project.name, @package_name, follow_multibuild: true) | ||
| @package = Package.get_by_project_and_name(@project.name, @package_name, | ||
| follow_multibuild: true, | ||
| follow_project_scmsync_links: Flipper.enabled?(:scmsync, User.session)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will expose readonly packages to all controllers that use this before action. I don't think this is a good idea.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added an scmsync specific method now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All this checking about Flipper.enabled?(:scmsync, User.session) getting a bit out of hand by now. Can you simplify this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did for the check_scmsync action
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
couldn't you normalize this between remote project and scmsync anyway?
What should we keep the regressions for remote projects and deal with different workarounds there?
(Technical, the only difference between an scmsync and a remote package on api level is just the permission handling for service run and lock. Everything else should be identical, including access to build states, log files and the rest of the commands).
There are multiple pull requests from me open fixing these regressions and come with test cases demonstarting the issues...
That link is bogus - see #18062 |
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hellcp-work-scmsync-package |
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hellcp-work-scmsync-package |
1 similar comment
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hellcp-work-scmsync-package |
3c821ff to
ccaea2b
Compare
ccaea2b to
64c881c
Compare
Displaying a reduced view of the packages coming from the remote scm
